home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Atari Mega Archive 1
/
Atari Mega Archive - Volume 1.iso
/
lists
/
gem
/
l_1199
/
1114
< prev
next >
Wrap
Internet Message Format
|
1994-08-27
|
2KB
Date: Fri, 29 Jul 94 08:48:13 BST
From: d.oakley.kid0111@oasis.icl.co.uk
Subject: RE: Re: Scope of an APP_DEFS file
To: gem-list@world.std.com
Precedence: bulk
Kev,
Windows in Dialogs is in my list because programs like Interface
allow you to have modal dialogs in windows or just dialogs. The
advantage of not using dialogs is speed - when you are updating
20 items and have to bring up a dialog for each one, the small
wait involved while the window draws can get annoying.
This is all up for debate but things like that are usually saved in the
program's own preferences file, and I take it that APP_DEFS conforming
programs will not use their own preference files: Am I right or wrong?
It all depends on how much application specific stuff we have in APP_DEFS:
my StormTracker program would probably have about 8 extra options in the
file with things such as Update Windows in Background, Show Spectrum
Analyser and Playback Quality.
Myself I do think a program should be able to update its lines in an
APP_DEFS file, otherwise you would have to exit the program before you
could save changes; I'd rather use my own prefs file for most things if
that was the case.
The .Xdefaults file's way of specifying shift keys if very sensible:
<Ctrl>Q
<Shift><Ctrl>P
<Alt>A
this makes parsing the line easy: if the next character is a '<' then read
until '>' for a shift key; otherwise we've found the basic keypress.
This gives you
StormTracker.Quit: <Ctrl>Q
StormTracker.GotoEnd: <Ctrl>Home
StormTracker.PlayFrequency: 12
Which is also a lot more readable
Seeya!
David